home *** CD-ROM | disk | FTP | other *** search
- Path: wormer.fn.net!sysadmin@wormer.fn.net
- From: withheld@keepitpublic.com (Rusty Meathook)
- Newsgroups: comp.lang.c
- Subject: Re: Stylistic Concerns with Header Files
- Date: Sun, 21 Apr 1996 21:09:43 GMT
- Organization: Feist Connections
- Message-ID: <4le152$bt@wormer.fn.net>
- References: <4lb9bl$amo@wormer.fn.net> <4ldjr2$88p@sparcserver.lrz-muenchen.de>
- NNTP-Posting-Host: mark411.fn.net
- X-Newsreader: Forte Agent .99b.112
-
- watzka@stat.uni-muenchen.de (Kurt Watzka) wrote:
-
- >withheld@keepitpublic.com (Rusty Meathook) writes:
- >
- >>The obvious problem, now, is that a source file that needs to use
- >>"foo.h" will have to include "bar.h" prior to including "foo.h", which
- >>is a nasty situation stylistically. Including another header file
- >>within a header file is even worse.
- >
- >Why is this "worse"? You either have to include header files in a
- >certain order, or every header file has to include all the header
- >files needed by that header file. The
-
- Hmmmmmm... not sure; I was under the impression that including one
- header file inside another was "taboo" or something. Apparently it's
- not, so I guess my problems are solved. :)
-
- >From a maintainers point of view, I prefer this scheme over having
- >to know which other header files have to be included before you can
- >include a given header file.
-
- Good point. Thanks!
-
-